feat(cloud-agent): show workspace commits in chat - #5816
Conversation
48cfccf to
d1bb6ea
Compare
d1bb6ea to
0d6eac7
Compare
0d6eac7 to
75af89c
Compare
75af89c to
ffe3bff
Compare
ffe3bff to
0940760
Compare
0940760 to
9235401
Compare
9235401 to
7dd0184
Compare
7dd0184 to
a1d986b
Compare
82b6a08 to
84d0471
Compare
3967df3 to
b1f7a33
Compare
b1f7a33 to
39353f1
Compare
39353f1 to
8cf151f
Compare
8cf151f to
991c8b7
Compare
3543e62 to
799233a
Compare
Code Review SummaryStatus: 1 Issue Found | Recommendation: Address before merge Executive SummaryThe SDK commit deduplication returns before updating commit status, so a replayed Overview
Issue Details (click to expand)WARNING
Files Reviewed (39 files)
Fix these issues in Kilo Cloud Previous Review Summaries (5 snapshots, latest commit 535333c)Current summary above is authoritative. Previous snapshots are kept for context only. Previous review (commit 535333c)Status: No Issues Found | Recommendation: Merge Executive SummaryIncremental review of Files Reviewed (2 files)
Previous review (commit 8bb8e9e)Status: 2 Issues Found | Recommendation: Address before merge Executive SummaryThe incremental commit reverts the commit-memo comparator to its original form, resolving the hidden-tab finding; the two previously reported issues in Overview
Issue Details (click to expand)WARNING
SUGGESTION
Files Reviewed (3 files)
Fix these issues in Kilo Cloud Previous review (commit e65de57)Status: 3 Issues Found | Recommendation: Address before merge Executive SummaryThe commit-evidence reader can throw on an out-of-range committer timestamp and silently drop a landed commit from the transcript; two lower-severity web regressions (hidden-tab memo skip, removed saved-file read-only cues) round out the findings. Overview
Issue Details (click to expand)WARNING
SUGGESTION
Files Reviewed (37 files)
Fix these issues in Kilo Cloud Previous review (commit 576895d)Status: No Issues Found | Recommendation: Merge Reviewed the PR against the current head Files Reviewed (37 files)
Previous review (commit 799233a)Status: No Issues Found | Recommendation: Merge Files Reviewed (38 files)
Reviewed by deepseek-v4.1-flash · Input: 0 · Output: 0 · Cached: 0 Review guidance: REVIEW.md from base branch |
576895d to
e65de57
Compare
e65de57 to
8bb8e9e
Compare
pandemicsyn
left a comment
There was a problem hiding this comment.
lgtm, just one small one from the robot
- Show managed workspace commits as subdued transcript entries with hover/tap metadata details. - Preserve immutable commit identity, bounded actual messages, turn attribution, replay deduplication, and truthful push status. - Keep the existing saved worktree viewer; this feature does not add historical commit diffs. Restacked onto latest main and squashed to one commit.
535333c to
1e23c4d
Compare
| const parsedCommit = sessionCommitDataSchema.safeParse(event); | ||
| const commitHash = parsedCommit.success ? parsedCommit.data.commitHash : undefined; | ||
| if (parsedCommit.success) { | ||
| if (seenCommits.has(parsedCommit.data.commitHash)) return; |
There was a problem hiding this comment.
WARNING: The dedup early return also skips the status transition and notify().
seenCommits.has(...) correctly guards the commit record, but returning here jumps over the status block and notify() that follow. Service events are replayed on connect/reconnect (cloud-agent-transport.ts seeds fromId=0 so the Durable Object re-delivers the stored log), and autocommit_started / autocommit_completed are persisted with a plain insert (no entity-id dedup) in websocket/ingest.ts, so a replayed started can arrive after a completed that was already recorded. processAutocommitStarted (service-state.ts:577) resets status to { type: 'autocommit', step: 'started' }, and the replayed completed then returns here before restoring step: 'completed', leaving the commit indicator stuck on "Committing…" until some later event overwrites it. Restrict the dedup guard to the commits append so the status/notify() path still runs for repeat completions.
Reply with @kilocode-bot fix it to have Kilo Code address this issue.
Summary
Verification
No manual browser or live-provider tests were rerun during this restack. Existing feature work was restored from a named stash and integrated with the merged parent; the original local handoff and evidence remain excluded.
Visual Changes
Adds compact commit metadata disclosures in the transcript. No screenshots were captured or uploaded during this restack.
Reviewer Notes
Stacked on main as #5816, with #5817 on top. Four commits after rebase onto latest main. The rebase resolution preserves both upstream sibling-serialization cases and the new commit-identity tests.
Targeted lint and web/SDK/shared/service/wrapper typechecks passed. 926 distinct focused tests passed, including auto-commit/events, SDK projection, commit parsing, isolated web presentation, and six Workers-runtime replay/deletion-fencing tests with mocked external boundaries. Web tests omitted database setup and are not E2E evidence.
The additional standalone services/cloud-agent-next/test/tsconfig.json check is not clean: 711 diagnostics include existing mixed-runtime/mock typing and pending-feature fixture typing. The normal package typechecks pass; no broad test-project cleanup is included.